Configuring a Virtual Loopback IP Trunk overcomes a limitation that restricts the number of Analog Gateways that MiVoice Business can host to five. The limit is imposed by ARS, which supports a maximum of six routes per route list. The route lists are used to ensure that outgoing external calls (especially E911 calls) for hosted phones are routed through IP Trunking to the appropriate gateway.
All IP trunks have been successfully established between the host MiVoice Business system and all remote Analog Gateways.
All IP phones on the gateways are registered at the host MiVoice Business system.
The following example is the programming required at the Head Office system in Los Angeles. The branch offices serviced by the Analog Gateways are located in Chicago and New York. Although there are only two gateways in the example, the solution described can be extended to any number of gateways.
The Head Office is connected to the gateways over an IP trunk belonging to trunk group 10. Trunk Group 10 is in Route Number 20.
Programming the Head Office MiVoice Business system:
Create a virtual loopback IP trunk.
In the IP/XNET
Trunk Groups form
(
In the ARS
Routes form (
Program the virtual loopback trunk to insert a default account code.
In ARS
Digit Modification Plans form
(
Enter the required value for Number of Digits to Absorb. The value to use depends on how traffic is normally routed. Typically, 0 is expected.
In the ARS
Leading Digits form
(
For the purposes of the example, the digits programmed are as follows:
ARS leading digit 81 followed by 911 to route calls to the Chicago gateway
ARS leading digit 82 followed by 911 to route call to the New York gateway.
TIP: If the Analog Gateways are clustered, consider using CESID digits as the ARS leading digits followed by 911 to route calls to the appropriate gateway.
Map the specific ARS
leading digit from Step 3 to the corresponding account code index
in Default
Account Codes form
(
enter 81 next to account code index 1 for Chicago extension;
enter 82 next to account code index 2 for New York extensions
Associate extensions
at the gateways with the appropriate account code index in the
Station Attributes
form (
enter 1 in the Default Acct. Code field for Chicago extensions,
enter 2 in the Default Acct. Code field for New York extensions.
Create a route list to differentiate the local (Head Office) users from the gateway users based on Class of Restriction (COR).
In the ARS
Route Lists form
(
NOTE: Local users must be COR restricted to access the first choice only, while remote users must be restricted to the second choice only.
In the ARS
Digits Dialed form
(
The programming for the example would be as follows:
a) 911 or 9911 depending on the local dialing scheme. Select Route List 11 as the Termination Type and Number.
b) 81911 or 819911 and select the existing IP trunk route to Chicago as the Termination Type and Number
c) 82911 or 829911 and select the existing IP trunk route to New York as the Termination Type and Number
TIP: In the "Number of Digits to Follow" field for Step 7b and Step 7c, specify how many of the digits inserted by the default account code programmed in Step 4 should be absorbed.
Program similar 911 routing at the Chicago and New York gateways.
NOTE:
The maximum number of VoIP Calls specified in the ICP/PBX
Networking form (